Minutes, IBIS Quality Task Group 15 February 2022 12:00-13:00 EST (09:00-10:00 PST) ROLL CALL ANSYS Curtis Clark Intel Technology * Michael Mirmak Micron Technology * Randy Wolff Siemens EDA Weston Beal Signal Integrity Software: * Mike LaBonte Teraspeed Labs: * Bob Ross Zuken USA: Lance Wang Everyone in attendance marked by * NOTE: "AR" = Action Required. -----------------------MINUTES --------------------------- Mike LaBonte conducted the meeting. Call for IBIS related patent disclosures: - None Call for opens: - None Review of previous meeting minutes: Minutes from the February 8, 2021 meeting were reviewed. Bob Ross moved to accept the minutes. Michael Mirmak seconded the motion. Without objection, the minutes were approved. ARs: - AR: Bob Ross to post BUG228 Done. - AR: Bob Ross to post BUG229 Done. - AR: Bob Ross to post BUG230 Done. - AR: Bob Ross to post BUG231 Done. - AR: Mike LaBonte to send updated draft IBISCHK7.1.0 User Guide for review Done. - AR: Weston Beal to prepare presentation on IBIS Quality Specification and checklist No report. NEW ITEMS: IBISCHK710 development: Mike LaBonte showed the user guide WIP 4 draft. He said there was one message 6900 had no message type or message text, and it had been omitted from the table. Mike had to add missing E, W, and C type codes for 3 or 4 dozen messages that had them as blank in the spreadsheet. Bob Ross asked about the issue of messages that could be issued as more than one type, saying we had previously decided to list those once for each usage in the table. Mike showed an email on that topic, saying that there were at least 26 places in the code where a message might be issued different ways. In some cases the same message string might be printed as either an error or warning. In other cases the warning message would be slightly different, usually with the word "suspicious" in it. He said 3 utility functions returned status codes of GOOD, BAD, or UGLY. The UGLY return would signify either a missing quote in a quoted string, or extra characters or digits in a number. Those would usually print warning or caution messages. He recommended making no change to the tables, saying it would take significant effort to catalog all such variant messages. Bob agreed, noting that we already had threshold-based variant messages. We agreed to publish the user guide as reviewed. AR: Mike LaBonte to upload IBISCHK User Guide and message spreadsheet Parser bug reports: Bob Ross said 4 new bug reports had been posted and would be classified Friday. Michael Mirmak said one of the new bugs on the web page had a curly bracket that needed to be a square bracket. Michael asked if we could add a description line to the bug template. Bob said that would not automatically propagate to the web page because the file bugdir.txt provided the title, which he entered manually. Bob said we could change the template, but he was not sure if we should update old bug report files. Mike LaBonte felt that was not necessary. Michael said it would be good to have a web form that could be filled and submitted online. We agreed to ask the webmaster about that. It might need a privacy notice and reCAPTCHA verification. Michael said we would want to support attaching files too. Bob was concerned that people would upload testcases that were not reduced. Michael said a file size limit might help. Mike wondered if GitHub could be used. IBIS quality checklist: No discussion. Tabled topics (no discussion without motion): - BIRD181.2 - IBISCHK security fixes Randy Wolff moved moved to adjourn. Michael Mirmak seconded. Without objection the meeting ended. Meeting ended: 12:59 ET Next meeting February 22, 2022